Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This could improve the case of upstream dependencies that mess up the… #4982

Closed
wants to merge 2 commits into from

Conversation

matteius
Copy link
Member

This adds error handling around badly formed python specifiers which pip happily installs the packages for, and the resolver spits out whatever is in the setup.py, however it will be wrongly parsed when quoted. My proposal here is that we simply alert the user and proceed to finish their package locking, since the python specifier is hardly the most important part of the Pipfile.lock. Even the current specifiers are non deterministic in Pip 21.x which we have other issue reports about and seems to be resolved in Pip 22.x.

The issue

#4681

The fix

Try/except and Alert/continue

The checklist

  • Associated issue
  • A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

…ir python specifiers by not failing locking entirely.
@matteius
Copy link
Member Author

matteius commented Mar 13, 2022

@frostming If you think this is the right approach as I am beginning to think, then I can add a news fragment and a test that shows locking succeeds when the python specifier is broken. Easiest thing to do would be use exotic==1.10.0 as the test case, but the problem there is it would take a while for just that one test to run and the suite already takes too long.

@matteius matteius added the Status: Deferred / On Hold 🛑 This item is on hold until further notice. label Mar 19, 2022
@matteius
Copy link
Member Author

Deferring this until the split-utils branch gets merged, and I'll rebase this change off where this util got moved to.

@matteius matteius closed this Sep 3, 2022
@matteius matteius deleted the issue-4681-gracefully-proceed-with-error branch September 3, 2022 23:35
@matteius
Copy link
Member Author

matteius commented Sep 3, 2022

Replacement PR: #5329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Deferred / On Hold 🛑 This item is on hold until further notice.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant